2.1.1. Reschedules

Additionally we have issues with other vendors who send a new rule on reschedule of recurring meeting. Reschedules are problematic for us with interop with other vendors. THe other vendors want to remove the old set and replace it with the new set, but we don’t allow that. We preserve the original set and try to move it to the new dates.times, but that isn’t always possible if the new set that’s sent has fewer/more instances than the original one.

Removing an invitee (not strictly specific to recurring): For removing an invitee (which was bundled in with CANCEL), we do not increment sequence number on the instance (recurring or single actually) so that we can add that user back into the meeting later. If we increment the sequence number on removal, then when we try to see who is coming to our meeting, the sequence #’s will no longer match up — that data is stale now. The responses will be off by 1 (from the removal). Remove should be a separate workflow event, not requiring a bump of sequence number, be it repeating or single.